home *** CD-ROM | disk | FTP | other *** search
- Path: news.crystalball.com!news
- From: Larry Weiss <lfw@oc.com>
- Newsgroups: comp.arch.embedded,comp.lang.c
- Subject: Re: Using malloc of C on embedded system?
- Date: Mon, 01 Apr 1996 11:26:28 -0600
- Organization: ...
- Message-ID: <316011C4.14F7@oc.com>
- References: <4jml7h$cbc@castor.usc.edu> <4jmr2uINN3cm@keats.ugrad.cs.ubc.ca>
- NNTP-Posting-Host: external.oc.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0 (Win16; I)
-
- Kazimir Kylheku wrote:
- >
- > In article <4jml7h$cbc@castor.usc.edu>,
- > Stannon Yen <chuitiny@castor.usc.edu> wrote:
- > >Is it possible to use C function malloc and free on system that has no OS?
- > >How can I setup the memory pool for dynamic allocation/deallocation of memory?
-
- >
- > Here is where the ISO standard's distinction between a ``hosted'' and
- > ``freestanding'' implementation comes in handy.
- > Presumably, the embedded development environment is freestanding, which means
- > that you are allowed to define your own malloc() function with external
- > linkage.
- >
-
-
- This "freestanding" aspect is something we don't talk too much about here.
- All treatment of any function is implementation or user defined.
- Even void main() is allowed. 8-)
-
- When reading K&R2 or the Schildt books, just keep telling yourself "this is
- written with respect to a freestanding implementation, so they can say anything
- they want about their implementation of the library".
-